From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] the proper way of determining the encoding
Date: Wed, 16 Jan 2008 09:51:54 +0100 [thread overview]
Message-ID: <1200473352-sup-5980@ausone.local> (raw)
In-Reply-To: <1200452938-sup-9442@south>
Excerpts from William Morgan's message of Wed Jan 16 04:09:48 +0100 2008:
> Reformatted excerpts from William Morgan's message of 2008-01-15:
> > Reformatted excerpts from nicolas.pouillard's message of 2008-01-15:
> > > And I don't see your gettext patch neither on master nor on next ;(
> >
> > Whoops, I had never merged it onto next in the first place. Well, it's
> > on master now. Let me know if it gives you any trouble.
>
> Aaaand merged onto next. I do seem to spend a lot of my time merging
> from master to next. I wonder if that's proper git usage. Seems to
> clutter up my pretty gitk graph.
I don't know the proper git usage, but I think that you should make all you
commits on next, apply all patches from users on next, and then cherry-pick
changes from next to master when they are well tested.
--
Nicolas Pouillard aka Ertai
next prev parent reply other threads:[~2008-01-16 8:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 21:46 Giorgio Lando
2008-01-07 6:04 ` William Morgan
2008-01-07 8:44 ` Giorgio Lando
2008-01-07 8:51 ` Giorgio Lando
2008-01-09 18:00 ` William Morgan
2008-01-10 0:39 ` Giorgio Lando
2008-01-13 2:22 ` William Morgan
2008-01-13 13:09 ` Giorgio Lando
2008-01-15 16:30 ` Grant Hollingworth
2008-01-16 1:45 ` William Morgan
2008-01-16 2:20 ` Nicolas Pouillard
2008-01-16 2:57 ` William Morgan
2008-01-16 3:09 ` William Morgan
2008-01-16 8:51 ` Nicolas Pouillard [this message]
2008-01-16 3:14 ` Nicolas Pouillard
2008-01-16 3:23 ` William Morgan
2008-01-16 3:28 ` Nicolas Pouillard
2008-01-16 3:38 ` William Morgan
2008-01-16 8:46 ` Nicolas Pouillard
2008-01-18 16:40 ` Nicolas Pouillard
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=1200473352-sup-5980@ausone.local \
--to=nicolas.pouillard@gmail.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