From: "Santi Béjar" <santi@agolina.net>
To: Pascal Obry <pascal@obry.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Finding the name of the parent branch?
Date: Fri, 30 Jan 2009 15:46:27 +0100 [thread overview]
Message-ID: <adf1fd3d0901300646h39e27f50pdb6510083284cf8a@mail.gmail.com> (raw)
In-Reply-To: <a2633edd0901300606ub4c507bocccb6747b436f01f@mail.gmail.com>
2009/1/30 Pascal Obry <pascal@obry.net>:
>> At least part of. You have to understand the branch model:
>>
>> git model:
>> * a branch is just a pointer to a commit
>> * you cannot say "this commit was done in that branch"
>> * what you can say is "this commit is contained in that branch"
>
> The second point wasn't clear to me.
A practical example:
$ git clone path/to/project.git
$ cd project
$ git checkout -b bugfix-1234 origin/master
$ # hack, hack, hack
$ git commit -a -m "Fix for the Bug #1234"
$ git push origin HEAD:master
So, you've done a commit in a local branch named bugfix-1234 and once
you push it to the master branch in origin there is nothing to tell
you so. A commit is defined with the current state, the old commit(s)
and some metadata (author and committer) but nothing about which
branch it was made, and as a branch is a pointer to a commit there is
nothing more.
Santi
next prev parent reply other threads:[~2009-01-30 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 10:56 Finding the name of the parent branch? Pascal Obry
2009-01-30 11:18 ` Santi Béjar
2009-01-30 12:56 ` Pascal Obry
2009-01-30 13:16 ` Santi Béjar
2009-01-30 13:35 ` Pascal Obry
2009-01-30 13:57 ` Santi Béjar
2009-01-30 14:06 ` Pascal Obry
2009-01-30 14:46 ` Santi Béjar [this message]
2009-01-30 13:35 ` Michael J Gruber
2009-01-30 14:26 ` Thomas Koch
2009-01-30 15:58 ` Pascal Obry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adf1fd3d0901300646h39e27f50pdb6510083284cf8a@mail.gmail.com \
--to=santi@agolina.net \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).