From: Junio C Hamano <gitster@pobox.com>
To: Fengguang Wu <wfg@linux.intel.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org, linux-raid@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: drivers/block/cpqarray.c:938:2: error: too many arguments to function 慴lk_rq_map_sg�
Date: Thu, 14 Jun 2012 10:26:20 -0700 [thread overview]
Message-ID: <7vpq91erer.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120614092519.GA12482@localhost> (Fengguang Wu's message of "Thu, 14 Jun 2012 17:25:19 +0800")
Fengguang Wu <wfg@linux.intel.com> writes:
> If we can somehow tag the whole branch, it would be most convenient.
> Git can add description to a branch with
>
> git branch --edit-description [branch name]
>
> However I don't know how to retrieve that description on a remote
> branch..
The branch description is designed to be a place you leave your
temporary note locally outside the history, until you are ready to
set the contents of the branch in more permanent storage (e.g. by
merging it to an integration branch, or sending pull requests for
it) at which time the information is consumed (e.g. inserted in the
merge commit message or pull request message). The history exchange
via "git push" / "git fetch" is by definition about exchanging the
history, and will not transfer branch descriptions.
For shared and more permanent notes, "git notes" may be more
suitable vehicle.
next prev parent reply other threads:[~2012-06-14 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4fd91c3f.KAwMcygw9fFGn9Cx%wfg@linux.intel.com>
[not found] ` <4FD984F3.3070502@kernel.dk>
[not found] ` <20120614090151.GA12013@localhost>
[not found] ` <4FD9A95D.40903@kernel.dk>
2012-06-14 9:25 ` drivers/block/cpqarray.c:938:2: error: too many arguments to function 慴lk_rq_map_sg� Fengguang Wu
2012-06-14 17:26 ` Junio C Hamano [this message]
[not found] ` <20120614100205.GA13217@localhost>
[not found] ` <4FD9C0D2.20500@kernel.dk>
2012-06-14 11:31 ` drivers/block/cpqarray.c:938:2: error: too many arguments to function lk_rq_map_sg Fengguang Wu
2012-06-14 11:52 ` Tomas Carnecky
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=7vpq91erer.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=axboe@kernel.dk \
--cc=git@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wfg@linux.intel.com \
/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).