unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Nicolas Richard <youngfrog@members.fsf.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Use of git branches
Date: Fri, 06 Nov 2015 11:05:36 -0500	[thread overview]
Message-ID: <m2611fdsfj.fsf@newartisans.com> (raw)
In-Reply-To: <CAAeL0SQjqXhE9M=TLnWW01Gq8hvfVmk7r70Ex+BBV7rVB20Omw@mail.gmail.com> (Juanma Barranquero's message of "Fri, 6 Nov 2015 14:54:58 +0100")

>>>>> Juanma Barranquero <lekktu@gmail.com> writes:

> I know that some old branches (though not all) are perhaps of historical
> interest. But, isn't there any way to remove them and yet keep their content
> from being pruned? Tags or something?

You can move branches into a different "ref space" on the server (this is not
tested yet, but should give the idea):

    git push origin refs/remotes/origin/old-branches/foo:refs/history/branches/foo
    git push origin :refs/old-branches/foo

Historical branches are not fetched until you add the corresponding refspec to
your .git/config file:

    [remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	fetch = +refs/history/*:refs/remotes/origin/history/*

Now you can write:

    git log origin/history/branches/Boehm-GC

John

p.s. This same trick works for GitHub PRs, btw, by using:

       fetch = +refs/pull/*:refs/remotes/origin/pr/*

     Now allowing you to: git checkout -b pr/1233 origin/pr/1233



  parent reply	other threads:[~2015-11-06 16:05 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 [this message]
2015-11-07  2:02                 ` Juanma Barranquero

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=m2611fdsfj.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --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).