From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>,
Poky <poky@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/7] oe-git-proxy: Add a new comprehensive git proxy script
Date: Sun, 10 Feb 2013 10:25:38 -0800 [thread overview]
Message-ID: <5117E622.3080700@linux.intel.com> (raw)
In-Reply-To: <CADkTA4PvLPB9C_ornX0EAXVEQVRSX4v0VZbOfz=zTtgHai-O0A@mail.gmail.com>
On 02/09/2013 06:48 PM, Bruce Ashfield wrote:
> >> All those comments ought to be bellow --- or those will be included in
> >> commit log.
> >>
> >
> > Which is fine.
>
> Well, usually the log of the revisions are not included in the commit
> logs; any special reason for it to be done different?
>
>
> Randomly jumping in,
>
> It's not all that uncommon for kernel developers to keep the revision
> history
> in long logs. It's used as a way to track the intermediate history, give
> review credit .. or just "because".
>
> So while not always done, it isn't unheard of. I have no strong opinion one
> way or the other, just thought I'd throw that out!
I'll just leave that to the maintainer. If whoever pushes it objects,
they can drop it, or ask me to resend.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-02-10 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 22:27 [PATCH V3 0/7] Git proxy handling updates (now with socat) Darren Hart
2013-02-08 22:27 ` [PATCH 1/7] oe-buildenv-internal: Remove GIT variables from BB_ENV_EXTRAWHITE Darren Hart
2013-02-08 22:27 ` [PATCH 2/7] oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITE Darren Hart
2013-02-08 22:27 ` [PATCH 3/7] base.bbclass: Remove generate_git_config() Darren Hart
2013-02-08 22:27 ` [PATCH 4/7] oe-git-proxy: Add a new comprehensive git proxy script Darren Hart
2013-02-09 2:43 ` Otavio Salvador
2013-02-09 16:59 ` Darren Hart
2013-02-09 17:02 ` Otavio Salvador
2013-02-10 2:48 ` Bruce Ashfield
2013-02-10 18:25 ` Darren Hart [this message]
2013-02-08 22:27 ` [PATCH 5/7] meta-yocto: Document new oe-git-proxy in site.conf.sample Darren Hart
2013-02-08 22:27 ` [PATCH 6/7] oe-git-proxy*: Remove previous git proxy solutions Darren Hart
2013-02-08 22:27 ` [PATCH 7/7] oe-git-proxy: Use socat instead of BSD nc Darren Hart
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=5117E622.3080700@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=poky@yoctoproject.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