login
Header Space

 
 

Re: dangling commits.

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Dave Jones <davej@...>
Cc: <git@...>
Date: Saturday, May 20, 2006 - 7:19 pm

On Sat, 20 May 2006, Dave Jones wrote:

Nothing, except

 - you used rsync to fetch the thing (so you get all objects, regardless 
   of whether they are reachable or not)

 - junio re-bases his "pu" branch, and I just end up following him (I 
   should stop exporting git entirely, here's no point, really). Thus, 
   whenever "pu" gets reset to something else, the old head of pu gets 
   dropped on the floor and ends up as a "dangling" commit (no branch head 
   points to it any more).

The moral(s) of the story being that

 (a) dangling commits are normal if you reset branch heads (which includes 
     things like "git rebase", for example)

 (b) rsync is not a good transfer protocol, since it will just blindly 
     transfer objects that aren't needed - or worse - successfully clone a 
     corrupt repository.

but there's nothing to _worry_ about in this particular schenario.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
dangling commits., Dave Jones, (Sat May 20, 7:05 pm)
Re: dangling commits., Linus Torvalds, (Sat May 20, 7:19 pm)
Re: dangling commits., Dave Jones, (Sat May 20, 7:49 pm)
Re: dangling commits., Sean, (Sat May 20, 7:08 pm)
speck-geostationary