Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
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 18:45:20 +0000	[thread overview]
Message-ID: <AANLkTin_eTz=qprMhm3v4nfpuhSk55VmCgmeHKht4EAH@mail.gmail.com> (raw)
In-Reply-To: <1297953902-sup-8049@meteor.durcheinandertal.local>

> While reimporting all my messages I encountered a few problemes with
> the GPGME code. Please consider the attached fixes.

0001-Encode-multipart-messages-for-crypt-operations.patch already
appears to be in master ...

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).

I imagine you would like them to be in your name, so I have not pushed
them yet. If anyone could tell me how I should be applying them
properly then I will do. And maybe it might be necessary to format the
patches with options that give more context.

I'm hoping someone with more git knowledge than me can help ...

Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-02-17 19:59 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 [this message]
2011-02-17 20:44   ` Gaudenz Steinlin
2011-02-17 22:57     ` Hamish D

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='AANLkTin_eTz=qprMhm3v4nfpuhSk55VmCgmeHKht4EAH@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