[llvm-dev] Switching to git (Windows experience) (was re:[cfe-dev] GitHub anyone?)
Nathan Jeffords via llvm-dev
llvm-dev at lists.llvm.org
Fri Jun 3 08:04:51 PDT 2016
My experience with git on windows over the last several years has been very
positive. I use TortoiseGIT for the bulk of my tasks. I like the fact that
I can perform most operations directly from the log window. I also use
git-gui (which is part of the base git installation) to do commits on
subsets of changes in a file, or a large number of separate commits in
quick succession. I find that I rarely need to use the command line as
tortoise git covers all the common commands, and a large number of the
uncommon ones. For LLVM I have used the unofficial, and now official git
mirrors for quite some time without issue (though I don't do very much with
it as I am not a regular contributor).
On Fri, Jun 3, 2016 at 7:50 AM Renato Golin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On 3 June 2016 at 15:42, Craig, Ben via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > Coming from a perforce and SVN background, I think this is
> > With perforce and SVN, you just don't have as many options and possible
> > workflows, so they tend to be a little easier to learn, and a lot easier
> > wrap in a UI on the client side.
> So, we just have to make sure that we don't add any crazy workflow on Git.
> That's why I like the idea of having llvm-projs as being an automated
> sub-module hook-driven repo that no one uses, and let everyone else
> use Git as it was intended, in a way that most GUIs can handle.
> That's the workflow I'm looking for... I *really* don't want a
> convoluted workflow "just because it's Git".
> I'd rather use Git-SVN than have to write tons of bash scripts and
> break my workflow. In that sense, we're on the exact same predicament.
> GUI or not, makes no difference.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev