Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Nov 2012 23:05:40 -0800
From:      perryh@pluto.rain.com (Perry Hutchison)
To:        utisoft@gmail.com
Cc:        fidaj@ukr.net, gmx@ross.cx, grarpamp@gmail.com, freebsd-hackers@freebsd.org
Subject:   Re: FreeBSD needs Git to ensure repo integrity [was: 2012 incident]
Message-ID:  <50a8eb34.5pMwq6kSsi47QgKI%perryh@pluto.rain.com>
In-Reply-To: <CADLo838oG26KmfHJ%2BtLh82GoJzzRtfqy69%2BNny1_DC8F8X4POQ@mail.gmail.com>
References:  <CAD2Ti29UoFcHendR8CcdQ4FPNW1HH0O47B1i3JW00Lke2m2POg@mail.gmail.com> <20121117221143.41c29ba2@nonamehost> <op.wnxq9eo0g7njmm@michael-think> <CADLo838oG26KmfHJ%2BtLh82GoJzzRtfqy69%2BNny1_DC8F8X4POQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
[trimmed some of the lists]

Chris Rees <utisoft@gmail.com> wrote:
> ... git doesn't work with our workflow.

I'm sure the workflow itself is documented somewhere, but is
there a good writeup of _how_ git doesn't work with it, e.g. what
capabilit{y,ies} is/are missing?  Seems this might be of interest
to the git developers, not because they necessarily want to support
FreeBSD as such, but as an example of a real-world workflow that git
currently does not handle well.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50a8eb34.5pMwq6kSsi47QgKI%perryh>