[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pan-users] The "no-break-space" problem, aka "blank" posts, that sh

From: K. Haley
Subject: Re: [Pan-users] The "no-break-space" problem, aka "blank" posts, that shouldn't be
Date: Sun, 27 Dec 2009 22:37:23 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20091204 Thunderbird/3.0

On 12/26/2009 6:10 PM, walt wrote:
> This is where I get confused. Is your own repo not identical to the one
> on  If not, how does know about those red and
> blue branches in the first place?
> I appreciate your help with pan -- if you don't have time to give us
> git lessons in addition, don't bother to reply.
I can try to explain this.

The short short version.  The diagrams for the branches I have pushed
are the same between github & my repo.  It simply doesn't have the other
branch names nor any of the commits for the other branches I have locally.

As you may know git tracks commits.  Each commit knows its parent(s). 
This is used to draw the graph.  Branches and tags are nearly the same
in git, both are just named references to a commit not part of the
commit.  The main difference is that tags are fixed while branches are
moved with every commit.  Each repo keeps its own list of branches.  A
'git push foo' will first send all the commits needed for branch foo,
then it will either create or update branch reference foo.

That should be clear as mud.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]