From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Update git/git-native
Date: Mon, 17 Nov 2008 20:25:48 -0500 [thread overview]
Message-ID: <20081118012548.GA7967@denix.org> (raw)
In-Reply-To: <87myg1g1pn.fsf@neumann.lab.ossystems.com.br>
On Sat, Nov 15, 2008 at 12:30:44AM -0200, Otavio Salvador wrote:
> Denys Dmytriyenko <denis@denix.org> writes:
>
> > I'm not sure if there is some requirement to stick with 1.5.x version of git,
> > if not the latest stable version is 1.6.0.4 - I am attaching patches for both
> > just in case, with corresponding ticket #4835.
> >
> > Please provide any comments.
>
> Well I'm more up to go with 1.6.0.4 for it so we have the latest
> version with all the latest bug fixes on it.
So, should I commit 1.6.0.4 only? Hope it won't break anyone's fetches.
--
Denys
next prev parent reply other threads:[~2008-11-18 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 0:56 [RFC] Update git/git-native Denys Dmytriyenko
2008-11-15 2:30 ` Otavio Salvador
2008-11-18 1:25 ` Denys Dmytriyenko [this message]
2008-11-18 15:19 ` Koen Kooi
2008-11-18 21:15 ` Denys Dmytriyenko
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=20081118012548.GA7967@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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