git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Carlos Pereira <jose.carlos.pereira@ist.utl.pt>
To: Ilya Bobyr <ilya.bobyr@gmail.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	git@vger.kernel.org, ikke@ikke.info
Subject: Re: howto to run git without a master branch
Date: Sun, 09 Mar 2014 23:58:59 +0000	[thread overview]
Message-ID: <531D0043.5060507@ist.utl.pt> (raw)
In-Reply-To: <531CE837.1080504@gmail.com>


> There is a "git remote set-head" to manipulate HEAD in a remote 
> repository.
Thanks, that is useful (like git symbolic-ref HEAD master-x suggested by 
Kevin, much better than editing the text file)
> I agree that this might be viewed as a user experience issue.
> But I can not come up with a possible solution.  Can you?
The branch where the user was when he/she pushed the repo to the server? 
it would be his/her responsibility to checkout the proper branch before 
pushing... if that was not good enough than he/she could always use git 
remote set-head... my point is: pointing to a bad branch that exists 
seems better than pointing to a branch that does not exist...

Anyway I agree this is not important, as we can easily change HEAD.
> I do not think there should be any issues.
Thank you very much for your answers,

Carlos

  reply	other threads:[~2014-03-09 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08 21:37 howto to run git without a master branch Carlos Pereira
2014-03-09  7:46 ` Torsten Bögershausen
2014-03-09 19:54   ` Carlos Pereira
2014-03-09 20:00     ` Kevin
2014-03-09 22:16     ` Ilya Bobyr
2014-03-09 23:58       ` Carlos Pereira [this message]
2014-03-10  9:30       ` Andreas Schwab

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=531D0043.5060507@ist.utl.pt \
    --to=jose.carlos.pereira@ist.utl.pt \
    --cc=git@vger.kernel.org \
    --cc=ikke@ikke.info \
    --cc=ilya.bobyr@gmail.com \
    --cc=tboegi@web.de \
    /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).