git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aneesh Bhasin <contact.aneesh@gmail.com>
To: git@vger.kernel.org
Subject: Adding a new file to all git branches
Date: Tue, 24 Mar 2009 09:11:15 +0530	[thread overview]
Message-ID: <f662f0210903232041p6f86b882of7b2d708946ea905@mail.gmail.com> (raw)

Hi,

I was wondering if it is possible to add a file to all the branches in
a repository without individually checking out each branch ?

A possible use-case for such a scenario is say I have a git repository
with various branches related to different features, versions or
bug-fixes and I want to be able to add a README file which contains
instructions/information common to all of those branches as of now
(but may diverge in future). So, do I have to checkout each branch
individually to add the same README file to all of them or is there a
direct/indirect workaround ?

Thanks for your help..

Regards,
Aneesh

             reply	other threads:[~2009-03-24  3:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  3:41 Aneesh Bhasin [this message]
2009-03-24  6:31 ` Adding a new file to all git branches 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

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

  git send-email \
    --in-reply-to=f662f0210903232041p6f86b882of7b2d708946ea905@mail.gmail.com \
    --to=contact.aneesh@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).