From: Juanma Barranquero <lekktu@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
Nicolas Richard <youngfrog@members.fsf.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Use of git branches
Date: Sat, 7 Nov 2015 03:02:34 +0100 [thread overview]
Message-ID: <CAAeL0SQdgmptzc7zsNrgHPgZgiCi8v5iCWN5sNNf+f2USqiiOA@mail.gmail.com> (raw)
In-Reply-To: <m2611fdsfj.fsf@newartisans.com>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
On Fri, Nov 6, 2015 at 5:05 PM, John Wiegley <jwiegley@gmail.com> wrote:
> You can move branches into a different "ref space" on the server (this is
not
> tested yet, but should give the idea):
[...]
> Now you can write:
>
> git log origin/history/branches/Boehm-GC
This is great. We should do that with all those old branches.
[-- Attachment #2: Type: text/html, Size: 485 bytes --]
prev parent reply other threads:[~2015-11-07 2:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151106085750.28172.54745@vcs.savannah.gnu.org>
[not found] ` <E1ZucqE-0007L0-MZ@vcs.savannah.gnu.org>
2015-11-06 9:33 ` [Emacs-diffs] master 2b316c0: ; * CONTRIBUTE: Add section about the bug tracker Juanma Barranquero
2015-11-06 9:49 ` Eli Zaretskii
2015-11-06 9:56 ` Juanma Barranquero
2015-11-06 10:10 ` Eli Zaretskii
2015-11-06 10:18 ` Juanma Barranquero
2015-11-06 10:44 ` Eli Zaretskii
2015-11-06 13:59 ` Juanma Barranquero
2015-11-06 14:27 ` Eli Zaretskii
2015-11-06 10:16 ` Use of git branches (was: [Emacs-diffs] master 2b316c0: ; * CONTRIBUTE: Add section about the bug tracker) Nicolas Richard
2015-11-06 10:46 ` Eli Zaretskii
2015-11-06 13:54 ` Juanma Barranquero
2015-11-06 14:56 ` Use of git branches David Kastrup
2015-11-07 1:57 ` Juanma Barranquero
2015-11-07 8:18 ` David Kastrup
2015-11-07 9:45 ` Juanma Barranquero
2015-11-06 16:05 ` John Wiegley
2015-11-07 2:02 ` Juanma Barranquero [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAeL0SQdgmptzc7zsNrgHPgZgiCi8v5iCWN5sNNf+f2USqiiOA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=youngfrog@members.fsf.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.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).