[rancid] Rancid and Git

[Crowe, David]

On Jul 19, 2014, at 1:16 PM, Heasley John <heas at shrubbery.net> wrote:

> Fri, Jul 18, 2014 at 02:57:07PM -0700, Crowe, David:
>> On Jul 18, 2014, at 2:18 PM, John Heasley <heas at shrubbery.net> wrote:
>> 
>>> Am Jul 18, 2014 um 2:05 PM schrieb "Crowe, David" <crowed at bendbroadband.net>:
>>>> 
>>>> i would agree with a single repo being the best approach.
>>>> 
>>>> regarding the automatic search for changed files (i'll include untracked files in here), the additions to .gitignore helps with this tremendously.
>>>> 
>>> 
>>> I do not like its global behavior,  but...
>>> 
>> 
>> that is a bit of a pain but once you add the extraneous files and patterns to .gitignore file i've not had to touch it in a long time.  having a separate repo for each group could make that a bit cleaner.
>> 
>> 
>>> Can you tell me what is wrong with the second approach i described?
>>> 
>> 
>> if i understand what you tried, the "remote" can't be within/under the same directory tree as $BASEDIR if that is the root of an existing git repo.
> 
> how do services like github arrange their store?  is it a path per-project?
> 

correct.

> another nice result of having this mehtod, is that the code remains generic
> for local (this host) or remote repositories.
> 

agreed.


>> if you stay with the single repo strategy, doing "git reset --hard $BASEDIR/group" is the best way to get back to the last known good repo copy for any group.
> 
> thanks; i suspected that would be the result.