From: Paul Menzel <paulepanter@users.sourceforge.net>
To: openembedded-devel@lists.openembedded.org
Subject: OT: `git am --scissors` (was: [PATCH] gtk+_2.20.1: add `pango-native` to `DEPENDS`)
Date: Sat, 09 Oct 2010 01:18:42 +0200 [thread overview]
Message-ID: <1286579922.4113.6.camel@mattotaupa> (raw)
In-Reply-To: <AANLkTim9By3dRuBbtOveONnCHOso+SvtE2mTt+5yg1SZ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
Am Freitag, den 08.10.2010, 08:24 +0200 schrieb Frans Meulenbroeks:
> 2010/10/8 Paul Menzel <paulepanter@users.sourceforge.net>:
> > Dear OE folks,
[…]
> > 8<-------------------------------------------------------------------->8
> > Date: Thu, 7 Oct 2010 13:43:58 +0200
> >
> > Since two or three days I am not able to build `gtk+_2.20.1.bb` anymore. I tried to revert to `gtk+.inc` 9730a2 [1] with
[…]
> And please also don't type things before the --- like "Dear OE folks.
> Please do explanations below that line, so if your patch is accepted
> people can just do a git am without the need to modify the commit
> message.
I actually formatted my message this way because it should still be
possible to use `git am`. Please take a look at the option `--scissors`
in `git help am` or git help mailinfo`.
[…]
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-10-08 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 1:22 [PATCH] gtk+_2.20.1: add `pango-native` to `DEPENDS` Paul Menzel
2010-10-08 6:24 ` Frans Meulenbroeks
2010-10-08 23:18 ` Paul Menzel [this message]
2010-10-09 7:17 ` OT: `git am --scissors` (was: [PATCH] gtk+_2.20.1: add `pango-native` to `DEPENDS`) Frans Meulenbroeks
2010-10-08 23:32 ` [PATCH] gtk+_2.20.1: add `pango-native` to `DEPENDS` Paul Menzel
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=1286579922.4113.6.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.