unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Xiangfu Liu <xiangfu.z@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: git push weird?
Date: Tue, 15 Jun 2010 19:54:07 +0200	[thread overview]
Message-ID: <878w6gnpvk.fsf@ambire.localdomain> (raw)
In-Reply-To: <4C17911F.5040506@gmail.com> (Xiangfu Liu's message of "Tue, 15 Jun 2010 22:41:35 +0800")

() Xiangfu Liu <xiangfu.z@gmail.com>
() Tue, 15 Jun 2010 22:41:35 +0800

   git is offline version control.
   so if you committed in local several times,
   when you git push. it will push all of your committed to server.

   hopt this can help.

Thanks.  I think i should have done a "git rebase" prior to "git push"
in order to isolate the one commit that i wanted to share.

In the meanwhile, i have also done:

  $ git push -v origin ttn/misc-maint
  Pushing to ssh://ttn@git.sv.gnu.org/srv/git/guile.git
  Enter passphrase for key '/home/ttn/.ssh/sv': 
  Total 0 (delta 0), reused 0 (delta 0)
  To ssh://ttn@git.sv.gnu.org/srv/git/guile.git
   * [new branch]      ttn/misc-maint -> ttn/misc-maint
  updating local tracking ref 'refs/remotes/origin/ttn/misc-maint'

I think it is ok for the branch ‘ttn/misc-maint’ to have many different
commits.  So now i would like to undo the damage on "master".  I think
only a project administrator is able to do that, however...

thi



  reply	other threads:[~2010-06-15 17:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 11:36 git push weird? Thien-Thi Nguyen
2010-06-15 14:41 ` Xiangfu Liu
2010-06-15 17:54   ` Thien-Thi Nguyen [this message]
2010-06-15 18:56 ` Ludovic Courtès
2010-06-15 19:39   ` Thien-Thi Nguyen
2010-06-15 20:56     ` Ludovic Courtès
2010-06-15 21:07     ` Andy Wingo
2010-06-15 21:56       ` Thien-Thi Nguyen
2010-06-15 22:15         ` Andy Wingo
2010-06-16  2:14           ` Thien-Thi Nguyen

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/guile/

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

  git send-email \
    --in-reply-to=878w6gnpvk.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-devel@gnu.org \
    --cc=xiangfu.z@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).