git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Subject: Re: direct ref manipulation
Date: Sun, 5 Sep 2010 18:36:39 -0500	[thread overview]
Message-ID: <20100905233639.GB18103@burratino> (raw)
In-Reply-To: <20100905232525.GA494@nibiru.local>

Hi Enrico,

Enrico Weigelt wrote:

> is there already an command for directly manipulating refs
> (eg. set a specific to given object id) ?

$ man git |grep ref
    Do not use replacement refs to replace git objects. See git-replace(1) for more information.
See the references above to get started using git. The following is probably more detail than necessary
    Move objects and refs by archive.
    Download objects and refs from another repository.
    Update remote refs along with associated objects.
    (deprecated) Recover lost refs that luckily have not yet been pruned.
git-pack-refs(1)
git-reflog(1)
    Manage reflog information.
    Create, list, delete refs to replace objects.
move objects and references between repositories.
git-symbolic-ref(1)
    Read and modify symbolic refs.
git-update-ref(1)
    Update the object name stored in a ref safely.
git-for-each-ref(1)
    Output information on each ref.
    List references in a remote repository.
git-show-ref(1)
    List references in a local repository.
git-check-ref-format(1)
    Ensures that a reference name is well formed.
...

Perhaps you are looking for git-update-ref.

Hope that helps,
Jonathan

  reply	other threads:[~2010-09-05 23:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 23:25 direct ref manipulation Enrico Weigelt
2010-09-05 23:36 ` Jonathan Nieder [this message]
2010-09-06  0:23 ` Nicolas Pitre

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=20100905233639.GB18103@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.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).