From: Santi <sbejar@gmail.com>
To: git <git@vger.kernel.org>
Subject: Re: [PATCH] branch: write branch properties
Date: Sat, 30 Sep 2006 00:47:46 +0200 [thread overview]
Message-ID: <8aa486160609291547y583b01fdvd6ba6b0e031d19b@mail.gmail.com> (raw)
In-Reply-To: <87d59kok0l.fsf@gmail.com>
> [PATCH] branch: write branch properties
>
> If you want to work in the 'next' branch of git.git:
>
> $ git clone --use-separate-remote git://git.kernel.org/pub/scm/git/git.git
> $ cd git
> $ git branch next origin refs/heads/next
> ... work/edit/commit ...
> $ git pull
>
> and it merges from branch 'refs/heads/next' of origin.
>
Any comments on this?
Possible comments :D
- No comments
- Not interested
- Not interesting
- I like the idea but not the patch because...
- I like the patch but not the idea (?)
- Broken syntax. Could be done in this other way...
- Stop all this crazy things, just config all this manually!
- Start more crazy things, like...
- ...
Santi
prev parent reply other threads:[~2006-09-29 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 22:42 [PATCH] branch: write branch properties Santi Béjar
2006-09-24 23:00 ` Santi Béjar
2006-09-25 0:41 ` Santi Béjar
2006-09-29 22:47 ` Santi [this message]
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=8aa486160609291547y583b01fdvd6ba6b0e031d19b@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=git@vger.kernel.org \
/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).