Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Testers wanted: New gnus backend nnselect
Date: Fri, 28 Apr 2017 08:23:27 -0700	[thread overview]
Message-ID: <87lgqk5zf4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86a8707fdm.fsf@local.lan>

Harry Putnam <reader@newsguy.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> [...]
>
> Harry wrote:
>>> What would I do differently to get to this work in progress the
>>> discussion is about, feature/gnus-select?
>
> Eric replied:
>> Basically, go into your emacs repo, run "git checkout
>> feature/gnus-select", then run "make".
>
> Thanks... I did that and got this response:
>
>  $ git checkout feature/gnus-select
>
>   Branch feature/gnus-select set up to track remote branch
>   feature/gnus-select from origin.  Switched to a new branch
>   'feature/gnus-select'
>
> I didn't really understand what it meant but suspect it is just what I
> wanted.

It is!

> And now I guess for future I would go back to `git pull' and any changes
> in feature/gnus-select would be pulled too?
>
> Or do I need to do something different?

Nope, that's correct. "git pull" to fetch new changes, followed by
another "make". If you want to get back to master at any point, just
"git checkout master", and "make" again.

Thanks for testing!




  reply	other threads:[~2017-04-28 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  3:02 Andrew Cohen
2017-04-24 20:52 ` Eric Abrahamsen
2017-04-25  0:09   ` Andrew Cohen
2017-04-25  1:01     ` Andrew Cohen
2017-04-25 15:33     ` Eric Abrahamsen
2017-04-27 16:03 ` Harry Putnam
2017-04-27 18:24   ` Eric Abrahamsen
2017-04-28 14:53     ` Harry Putnam
2017-04-28 15:23       ` Eric Abrahamsen [this message]
2017-04-28 15:44         ` Harry Putnam
     [not found] ` <8eff03d9274e4d0fa58c85a87381706f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
     [not found]   ` <87vapp6izc.fsf@delle7240>
2017-04-28 15:34     ` Eric Abrahamsen
2018-04-11 19:44 ` Lars Ingebrigtsen

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=87lgqk5zf4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).