From: Hamish D <dmishd@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] GPGME fixes
Date: Thu, 17 Feb 2011 22:57:42 +0000 [thread overview]
Message-ID: <AANLkTikdMASiPmP6DFBpdAFNzK+w11Wf0Qq07MK1FsL8@mail.gmail.com> (raw)
In-Reply-To: <1297974845-sup-4146@meteor.durcheinandertal.local>
>> I like the others though, though in applying them I ran into some
>> trouble, partly through my adding lines near the top of the file that
>> change line numbers and seemed to confuse git. So they are now applied
>> to a local copy, but in my name (but with your commit messages).
>
> What command do you use to apply the patches? If I can fetch your
> changes somewhere I can also rebase my patches on top of them.
My changes are on the gpgme branch on gitorious. I used the git apply
command. I also tried git am but that did't work at all.
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-02-17 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 14:49 Gaudenz Steinlin
2011-02-17 18:45 ` Hamish D
2011-02-17 20:44 ` Gaudenz Steinlin
2011-02-17 22:57 ` Hamish D [this message]
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=AANLkTikdMASiPmP6DFBpdAFNzK+w11Wf0Qq07MK1FsL8@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=sup-devel@rubyforge.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