Hi, I just screwed my repo and need advice on how to get it back.
I have been doing some major work on a project, and was finally ready to
push it. Foolish me did the work in master. So I go to push and I am told,
To prevent you from loosing history non-fast-forward updates were
rejected
Doing some research.
$ git reflog
6d86f4c HEAD@{0}: commit: Simplify configuration using RUBY_PATH. [major]
e6ca6f1 HEAD@{1}: commit: Step toward getting direct LEDGER references
out of Library.
7219018 HEAD@{2}: commit: Minor refactorings to Ledger class.
So I am thinking I just do:
Thanks guys! Very helpful information. Allowed me to be confident about
proceeding. Problem has been fixed and it went smoothly.
I am still not sure how the repo could have gotten in that state since I am
just about 100% positive there was no other push from anywhere. I will have
to
Somehow I have branch that was supposed to be a tag. Not sure how it ever
became a branch, but now that I have discovered it I am wondering, how do I
convert the branch into a tag?
Since the name will be the same for both the branch and the tag, I assume I
can just checkout the branch and tag
Might eat up a lot of space after a while. Plus how often is dropbox synced?
I'm not sure why you would want a local git repo in dropbox, since in this
case it is already backed-up on GitHub's servers.
--
You received this message because you are subscribed to the Google Groups Git
for human
Heroku is your friend if you have the $.
On Friday, March 30, 2012 2:04:40 PM UTC-4, Yves S. Garret wrote:
Hi,
My organization has fallen in love with cloud computing (yay,
progress, moving into the future!) What I would like to know is how I
can combine the cloud and Git. I'd love
Ok. That makes some sense.
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users/-/JiwrQLfEtUYJ.
To post to this group, send email to
I just added the complete contents of a directory to my project, and
committed.
$ git add foo/
$ git commit -m Add foo.
Then I realized that I actually did not want to add all those files. So I
tried to step back with:
$ git reset --hard HEAD^
Git rolled back the commit okay, but also
I figured it out.
$ git reflog
Then
$ git checkout -b someName shaOfResetCommit
Thankfully git doesn't actually delete anything for some 90 days after the
fact.
My mistake was to use `--hard`, but I didn't think it would delete the
files b/c there were not being tracked before this
On Sunday, December 11, 2011 3:13:44 PM UTC-5, Konstantin Khomoutov wrote:
Patching a tag sounds odd for a system which is about keeping immutable
objects referencing each other by cryptographic hashes of their
contents.
Unfortunately, git-tag seems not to support anything like -c or -C of
Yep. Thanks. I've read it. But it only speaks of creating missing tags. I
was wondering if there is a way to adjust the data of an existing tag.
I can of course delete the tag and retag --which is what I am doing
presently. Unfortunately that means checking out previous tag, copy tag
message,
I simply don't understand:
$ git pull upstream master
From github.com:benbjohnson/smeagol
* branchmaster - FETCH_HEAD
Already up-to-date.
$ git push upstream master
To git(at)github.com:benbjohnson/smeagol.git
! [rejected]master - master
I'm not a bash expert, so I need to ask, who can I pipe a message
into the git tag command? I have a program that will return my latest
release notes.
$ pom news
... message ...
So I want to pipe that into git tag as the tag message. I've been
trying to figure it out. The docs say that there
On Jun 19, 1:46 pm, Peter Shenkin shen...@gmail.com wrote:
On Sat, Jun 19, 2010 at 1:24 PM, Trans transf...@gmail.com wrote:
I'm not a bash expert, so I need to ask, who can I pipe a message
into the git tag command? I have a program that will return my latest
release notes.
$ pom
Looks like git just pissed away all my work for the last two months.
I was doing everything like I normally do. I made my changes,
committed and 'git push origin master'. Everything looked good. Git
told me Everything up-to-date. But... I went over to the project's
github page
Sorry, make that:
$ git branch recentwork 8658a39
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
Hi--
I screwed up some tag messages and I need to go back and change them.
How does one do this?
Thanks.
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe
On May 7, 7:57 am, Konstantin Khomoutov khomou...@gmail.com wrote:
On May 7, 12:51 am, Trans transf...@gmail.com wrote:
I notice that almost every tagging example uses a version number with
a prefixed 'v', e.g.
$ tag -a -m first major point release v1.0.0
I, on the other hand, have
I notice that almost every tagging example uses a version number with
a prefixed 'v', e.g.
$ tag -a -m first major point release v1.0.0
I, on the other hand, have never bothered with 'v' prefix, and have
always done, e.g.:
$ tag -a -m first major point release 1.0.0
Is there some reason to
?
Thanks,
~Trans
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more options, visit
On Feb 10, 5:13 pm, FlashWebHost.com flash...@gmail.com wrote:
Use hooks, here is what i use
[fsh...@server58 hooks]$ cat post-update
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, rename this file to
On Jan 6, 9:20 am, Michael P. Soulier msoul...@digitaltorque.ca
wrote:
On 05/01/10 Trans said:
So I've cloned a repo, which is a fork of another repo. If I want to
update my repo to match the original (and ditch any changes I may have
made), how do I do it?
Did you follow any workflow
Is there are way to add a custom property to commits? I want to use it
to track commit type For example, I use 'admin', 'doc', 'major',
'minor', and 'bug' to classify my commits.
Thanks.
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To
On Jan 1, 7:43 pm, Jeffrey jefr...@gmail.com wrote:
This sounds like precisely the purpose of standard formats for log
messages. The simplest thing would be to prefix the subject with
[type]: like this:
major: add big feature
or put it on the first line of the body, if you have
24 matches
Mail list logo
