From: "David S. Miller" <davem@davemloft.net>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 1/1][DCCP]: sparse endianness annotations
Date: Wed, 22 Feb 2006 00:58:12 +0000 [thread overview]
Message-ID: <20060221.165812.56872927.davem@davemloft.net> (raw)
In-Reply-To: <39e6f6c70602211630m52d57c43m5365835ebad48e0@mail.gmail.com>
From: "Arnaldo Carvalho de Melo" <acme@ghostprotocols.net>
Date: Tue, 21 Feb 2006 21:49:14 -0300
> Do you prefer? Today I talked with our git guy (Eduardo Habkost) and
> changed my mind, doing things (duh!) in "master" and using git-fetch/
> git-rebase to track your net-2.6.17 tree seems less noisy on Linus
> git log history :-)
I think I'm more likely to make mistakes if you use branches
_unless_ you list the branch in the URL like this:
--------------------
Please pull from:
$(GIT_URL) $(BRANCH_NAME)
--------------------
because I just copy&paste the line into a "git pull" command.
next prev parent reply other threads:[~2006-02-22 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 0:30 [PATCH 1/1][DCCP]: sparse endianness annotations Arnaldo Carvalho de Melo
2006-02-22 0:41 ` David S. Miller
2006-02-22 0:49 ` Arnaldo Carvalho de Melo
2006-02-22 0:58 ` David S. Miller [this message]
2006-02-22 1:27 ` Arnaldo Carvalho de Melo
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=20060221.165812.56872927.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dccp@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