Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Michael J Gruber
Junio C Hamano venit, vidit, dixit 14.04.2015 11:22: > Sebastian Schuberth writes: > >> On Tue, Apr 14, 2015 at 10:50 AM, Michael J Gruber >> wrote: >> >>> "to dangle" means "to hang loosely". >>> >>> So, in the description above, "A^ dangles from A loosely" because it >>> hangs from A (you can

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Sebastian Schuberth
On Tue, Apr 14, 2015 at 10:52 AM, Sebastian Schuberth wrote: >> A dangling object is an unreachable object that cannot be >> made reachable by any way other than pointing at it >> directly with a ref. > > Thanks a lot for the prompt explanation! Note to myself: I just realized that both "danglin

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Sebastian Schuberth
On Tue, Apr 14, 2015 at 11:22 AM, Junio C Hamano wrote: > I just visualize commits to be ping-pong balls with strings between > them, and then grab the root of the graph and lift the whole thing > up, while tips of the branches and tags are anchored. Commit A will > be dangling in the wind if yo

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Junio C Hamano
Sebastian Schuberth writes: > On Tue, Apr 14, 2015 at 10:50 AM, Michael J Gruber > wrote: > >> "to dangle" means "to hang loosely". >> >> So, in the description above, "A^ dangles from A loosely" because it >> hangs from A (you can reach it from A) but loosely, because it would >> "drop" if A ge

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Sebastian Schuberth
On Tue, Apr 14, 2015 at 10:50 AM, Michael J Gruber wrote: > "to dangle" means "to hang loosely". > > So, in the description above, "A^ dangles from A loosely" because it > hangs from A (you can reach it from A) but loosely, because it would > "drop" if A gets dropped and A is "likely" to be dropp

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Sebastian Schuberth
On Tue, Apr 14, 2015 at 10:05 AM, Junio C Hamano wrote: > A dangling object is an unreachable object that cannot be > made reachable by any way other than pointing at it > directly with a ref. Thanks a lot for the prompt explanation! -- Sebastian Schuberth -- To unsubscribe from this list: sen

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Michael J Gruber
Junio C Hamano venit, vidit, dixit 14.04.2015 10:05: > On Tue, Apr 14, 2015 at 12:16 AM, Sebastian Schuberth > wrote: >> Hi, >> >> reading through the fsck docs [1] I'm having a hard time understanding >> what the difference between "unreachable" and "dangling" objects are. >> >> By example, suppo

Re: git fsck: unreachable vs. dangling

2015-04-14 Thread Junio C Hamano
On Tue, Apr 14, 2015 at 12:16 AM, Sebastian Schuberth wrote: > Hi, > > reading through the fsck docs [1] I'm having a hard time understanding > what the difference between "unreachable" and "dangling" objects are. > > By example, suppose I have a commit A that is the tip of exactly one > branch (a

git fsck: unreachable vs. dangling

2015-04-14 Thread Sebastian Schuberth
Hi, reading through the fsck docs [1] I'm having a hard time understanding what the difference between "unreachable" and "dangling" objects are. By example, suppose I have a commit A that is the tip of exactly one branch (and no tag or other ref points to A). If I delete that branch, is A now dan