From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: any partial or rudamentary documentation of new nnselect work somewhere?
Date: Sun, 14 May 2017 09:21:21 -0400 [thread overview]
Message-ID: <86wp9jtvzi.fsf@local.lan> (raw)
In-Reply-To: <87a86gb1bc.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> What would be most useful is if someone could explain git
> better to me so that the rebase process was less bewildering :(
If no one responds to that... (and you've no doubt considered this)
But, you could take the query to gmane.comp.version-control.git
There are some heavy hitters there that can probably explain things
thouroughly.
The name of the group does not suggest it is a devel group but that
does appear to be mostly what is going on there. None the less, I've
seen many detailed questions answered there. Well out of my league.
But there are many true experts there that appear willing to answer
complicated question.
next prev parent reply other threads:[~2017-05-14 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 22:39 Harry Putnam
2017-05-07 0:10 ` Andrew Cohen
2017-05-10 20:49 ` Harry Putnam
2017-05-11 0:01 ` Andrew Cohen
2017-05-11 13:07 ` Harry Putnam
2017-05-12 1:18 ` Eric Abrahamsen
2017-05-13 13:44 ` Harry Putnam
2017-05-14 2:48 ` Eric Abrahamsen
2017-05-14 13:21 ` Harry Putnam [this message]
2017-05-14 13:24 ` Harry Putnam
2017-05-15 3:30 ` Eric Abrahamsen
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=86wp9jtvzi.fsf@local.lan \
--to=reader@newsguy.com \
--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).