From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>,
Constantin Musca <constantinx.musca@intel.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Versioning of git recipes (and incremental PR)
Date: Fri, 23 Nov 2012 19:45:09 +0000 [thread overview]
Message-ID: <1353699909.7352.2.camel@ted> (raw)
In-Reply-To: <CAP9ODKqPx8AE9O66ALLkpwXDFxr1outs_tdeDG2DnyZdw9Q=Ag@mail.gmail.com>
On Fri, 2012-11-23 at 17:23 -0200, Otavio Salvador wrote:
> I like to idea of a single updating place. What I dislike is AUTOINC
> not being taken care in the fetcher.
>
> In this case any GIT revision changes, the AUTOINC won't bump as usual
> (without PR server)?
Why do you need AUTOINC to bump? The only reason we have increments in
the fetcher is for package upgrading...
Cheers,
Richard
next prev parent reply other threads:[~2012-11-23 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 17:26 RFC: Versioning of git recipes (and incremental PR) Richard Purdie
2012-11-23 19:23 ` Otavio Salvador
2012-11-23 19:45 ` Richard Purdie [this message]
2012-11-24 13:55 ` Otavio Salvador
2012-11-25 21:21 ` Richard Purdie
2012-11-25 21:44 ` Otavio Salvador
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=1353699909.7352.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=constantinx.musca@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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