unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Rollins <jrollins@finestructure.net>
To: Xavier Maillard <xma@gnu.org>, Albin Stjerna <albin@eval.nu>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: running the crypto branch [was: Re: Hiding HTML mime-parts and/or scrubbing (gmail's) HTML-based citation]
Date: Sat, 26 Feb 2011 16:27:35 -0800	[thread overview]
Message-ID: <87r5aucoeg.fsf@servo.finestructure.net> (raw)
In-Reply-To: <m27hcmwdmf.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]

On Sun, 27 Feb 2011 01:00:08 +0100, Xavier Maillard <xavier@maillard.im> wrote:
> What is the easy way to switch to your codebase from notmuch mainline ?
> I mean, what exact commands do we need to type in order to use your
> branch code ? Knowing that would certainly help people in switching and
> testing your code.

Hey, Xavier.  Thanks for asking.  Here's what I would suggest:

1. Add my public repo as a remote in your notmuch git repository:

$ git remote add jrollins git://finestructure.net/notmuch

2. Update your remotes to pull in the remote branches

$ git remote update

At this point you should see my public branches as remote-tracking
branches in your repository, e.g.:

$ git branch -a
...
  remotes/jrollins/crypto
  remotes/jrollins/master
  remotes/jrollins/personal

3. Check out my crypto branch into a local branch:

$ git checkout --track jrollins/crypto

This will put you in a new local branch in your repository called
"crypto" that will be tracking my public crypto branch.

4. Compile notmuch in the crypto branch and install it, however you
usually do.  I do something like this:

./configure --prefix=~/opt/notmuch
make
make test
make install

I then run notmuch in emacs like this:

export LD_LIBRARY_PATH=~/opt/notmuch/lib:$LD_LIBRARY_PATH
emacs -L ~/opt/notmuch/share/emacs/site-lisp -f notmuch

I hope that helps.  Please let me know if you have any other questions.
And of course we'd love to hear any and all feedback on the new
cryptographic features!

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2011-02-27  0:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 18:19 Hiding HTML mime-parts and/or scrubbing (gmail's) HTML-based citation Albin Stjerna
2011-02-22 18:33 ` Daniel Kahn Gillmor
2011-02-22 19:42   ` Albin Stjerna
2011-02-22 19:59     ` Daniel Kahn Gillmor
2011-02-23  1:13       ` Rob Browning
2011-02-26 23:57         ` Xavier Maillard
2011-02-23 14:10       ` Albin Stjerna
2011-02-23 19:01         ` Jameson Rollins
2011-02-27  0:00           ` Xavier Maillard
2011-02-27  0:27             ` Jameson Rollins [this message]
2011-02-28 13:32               ` running the crypto branch [was: Re: Hiding HTML mime-parts and/or scrubbing (gmail's) HTML-based citation] Xavier Maillard

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r5aucoeg.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=albin@eval.nu \
    --cc=notmuch@notmuchmail.org \
    --cc=xma@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).