From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix spelling in variable documentation
Date: Fri, 14 Nov 2008 16:37:08 -0500 [thread overview]
Message-ID: <874p2ac7ln.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <B7FD54A9-AAF5-4D59-8924-66464CA22546@uva.nl> (Carsten Dominik's message of "Fri\, 14 Nov 2008 22\:33\:22 +0100")
Carsten Dominik <dominik@science.uva.nl> writes:
> On Nov 14, 2008, at 6:58 PM, Bernt Hansen wrote:
>
>> - org-remember-store-without-prompt
>> ---
>>
>> Minor typo fix in the documentation. This is available on the
>> git://git.norang.ca/org-mode repository on the 'for-carsten' branch.
>>
>> You can cherry pick commits easily with gitk as follows:
>>
>> $ git checkout master
>> $ git fetch git://git.norang.ca/org-mode for-carsten
>> $ gitk master FETCH_HEAD
>>
>> Then right-click on the commits on FETCH_HEAD and select 'Cherry-pick
>> this commit' from the menu. This adds the commit to your current
>> (master) branch.
>
> To the master? No matter on which branch I am? Or will it be added
> to the current HEAD?
>
> This is an awesome feature. Git is incredible.
It cherry picks to your current branch HEAD. You can checkout different
branches in gitk by right-clicking on the branch tag. You can also
create tags, and do various other useful operations.
You can also cherry pick manually with
$ git cherry-pick FETCH_HEAD^
There's nothing really special about the 'master' branch. It's just a
name and most repositories have a master branch - but you don't have to
have one of those. You can delete it, rename it to something else,
whatever - it's just a name.
Regards,
Bernt
next prev parent reply other threads:[~2008-11-14 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 17:58 [PATCH] Fix spelling in variable documentation Bernt Hansen
2008-11-14 21:33 ` Carsten Dominik
2008-11-14 21:37 ` Bernt Hansen [this message]
2008-11-14 21:43 ` Carsten Dominik
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874p2ac7ln.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=dominik@science.uva.nl \
--cc=emacs-orgmode@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://git.savannah.gnu.org/cgit/emacs/org-mode.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).