Subject: Re: [boost] [git] How the blazes are you supposed to update all the submodules?
From: Edward Diener (eldiener_at_[hidden])
Date: 2013-12-22 12:30:21
On 12/22/2013 11:08 AM, Paul A. Bristow wrote:
>> -----Original Message-----
>> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Beman Dawes
>> Sent: Saturday, December 21, 2013 2:48 AM
>> To: Boost Developers List
>> Subject: Re: [boost] [git] How the blazes are you supposed to update all the submodules?
>> On Thu, Dec 19, 2013 at 5:14 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
>>> No amount of scripting is going yo help those of us not wanting to use
>>> the git cli. And this is something I mentioned early on. If something
>>> past basic git functionality is needed as a regular course of use the
>>> move to git will fail.
>> TortoiseGit seems to work well in a submodule environment, although I've only used the "git
>> ..." equivalents a few times. I don't have any experience with the other Git GUI's, so can't speak
> for them.
> As someone who has been hiding his head under a blanket up till now (half hoping it would all go
> away ;-)
> I too very, very much trust that it will be possible to do all the routine things using a GUI, and
> that it will be fully documented using at least one GUI.
> Tortoise GIT has worked for me locally, so I'd favour using that for a start, but guidance from
> those with more experience will of course continue be helpful.
A number of the Tortoise Git dialogs do not give an explanation in the
help for some of the GUI options. This is sometimes supplemented in the
help by suggesting that one look at the equivalent git command which the
GUI dialog implements, but this is often a PITA if it is difficult to
map the GUI option to a particular git command line option.
TGIT is very decent and has been getting better with each release but it
is not as polished as TSVN. One can always of course drop down to the
git command line level. As I get better at git, from reading books and
documents, this becomes easier.