git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Julian Goacher <julian.goacher@gmail.com>
To: git@vger.kernel.org
Subject: Re: Modifying a bare repo directly
Date: Tue, 11 Apr 2017 22:35:17 +0100	[thread overview]
Message-ID: <CAG_DJY=3Q1hcGnD72hwhdHxVReD4g7JZou=cm32_WECoJf+5nA@mail.gmail.com> (raw)
In-Reply-To: <20170410182209.GA18358@dcvr>

Thanks for the replies; is there anything that needs to be known about
concurrent updates on a repo when using plumbing commands?

On 10 April 2017 at 19:22, Eric Wong <e@80x24.org> wrote:
> Julian Goacher <julian.goacher@gmail.com> wrote:
>> Is it possible to modify a bare repo directly? e.g. is it possible to
>> insert a file into a bare repo without first cloning a non-bare copy?
>> I'm thinking along the lines of a command or sequence of commands that
>> modifies the file index and then copies the file blob into /objects,
>> but in a situation where the new file exists separately from the
>> target repo.
>
> Yes.  You can use the commands Ævar and Jeff talked about as
> (those are probably the easiest).  "git fast-import" is also
> great to avoid using an index entirely; it can be much faster
> for mass modifications.

  reply	other threads:[~2017-04-11 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 10:09 Modifying a bare repo directly Julian Goacher
2017-04-10 10:33 ` Ævar Arnfjörð Bjarmason
2017-04-10 14:07   ` Jeff King
2017-04-10 18:22 ` Eric Wong
2017-04-11 21:35   ` Julian Goacher [this message]
2017-04-12  0:48     ` Jeff King

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG_DJY=3Q1hcGnD72hwhdHxVReD4g7JZou=cm32_WECoJf+5nA@mail.gmail.com' \
    --to=julian.goacher@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.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).