On Mon, Sep 02, 2013 at 09:59:43PM -0700, Juha Aaltonen wrote:
To put it more clearly:
There are a couple of guys working with a code and there's a common
repo on a server.
I cloned the remote repo with both Giteye and SourceTree (two
different clones).
I edited the code cloned with
If you want to keep your process relatively similar then I think it might
look something like...
development (repo)
- master (= trunk)
- branches from master.
- tags on master.
de (repo)
- master (= trunk)
- branches from master (if necessary, probably a good practice to create
a
Your email client seems to be set to sending HTML-only, which means my
email client wasn't able to display the illustration of the SVN repo
properly. I've hopefully guessed correctly in my attempt to adjust it
below ;)
On Mon, Sep 02, 2013 at 10:40:55PM -0700, Sascha Egerer wrote:
Hi,
we are
Thanks for the input guys. We could do an automatic sync with manual
notifications on merge conflicts (would probably be rare), but I think we
will smplify our setup like Konstantin suggests.
For reference:
* We have many readers of the repo in zone two, so we set up a clone
--mirror as a read
*I manually loaded a few files in my repository and some files are now
ignored without being specified as ignored in gitignore.*
*here is a brief discussion on stack overflow on this issue. We suspect
this is a bug.*
*
*
I manually replaced come files in a dev repo and not i have a few files
ignored without add these files to gitignore. We suspect this is a bug,
here is a discussion that prompted this post.
http://chat.stackoverflow.com/rooms/36566/discussion-between-xdrone-and-jszakmeister
--
You received
Hi Dexter,
you are using option x in git clean command. In the manual, the option x
tells:
-x
Don’t use the standard ignore rules read from .gitignore (per
directory) and $GIT_DIR/info/exclude, but do still use the ignore rules
given with -e options. This allows removing all
thank you all very much for your responses this is the first time I'm
back on Usenet in a long time... it had become practically unusable b/c of
the spam, but I see that google got its act together here, and has somehow
managed to deal with the spam...;-) this is good to know...
yes, I
If you don't want to do a commit, then do a stash. It puts the current
working directory off to the side. Like a temporary branch. When you want
to come back, then you do a git stash pop.
I think I understand how you're working. You likely only do a commit when
you think something is finished. I,
Hello!
I get with git log --format=%h %ci %s
eef5296 2013-08-15 16:37:35 +0200 msg3
1e68ecb 2013-08-14 11:08:22 +0200 msg2
4959e91 2013-07-29 12:03:09 +0200 msg1
How can I achieve this output please?
eef5296 2013-08-15 16:37 msg3
1e68ecb 2013-08-14 11:08 msg2
4959e91 2013-07-29 12:03 msg1
Or
On Tue, 2013-09-03 at 08:05 -0700, maya melnick wrote:
but I imagine in other situations, to have to commit every time before
switching branches is weird... what if you haven't finished work on a
branch and need to switch branches to take care of another problem,
but don't want to commit what
From: maya melnick maya778...@yahoo.com
(I haven't commited, it's just a test branch, I don't want to commit;-)
make sense?
The way to think about it is that you've just changed a file in the
working directory, it isn't *in* the branch or the repository. So
when you tell Git to
On Tue, 3 Sep 2013 10:20:06 -0500
John McKown john.archie.mck...@gmail.com wrote:
If you don't want to do a commit, then do a stash. It puts the current
working directory off to the side. Like a temporary branch.
This comparison is quite to the point -- the `git stash` command even
allows to
On Tue, 3 Sep 2013 08:05:23 -0700 (PDT)
maya melnick maya778...@yahoo.com wrote:
[...]
but I imagine in other situations, to have to commit every time
before switching branches is weird... what if you haven't finished
work on a branch and need to switch branches to take care of another
On 4 September 2013 01:20, John McKown john.archie.mck...@gmail.com wrote:
If you don't want to do a commit, then do a stash. It puts the current
working directory off to the side. Like a temporary branch. When you want
to come back, then you do a git stash pop.
I think I understand how
For milestones, I either create a new branch at that commit point (rarely)
or tag the commit with a nice name.
On Tue, Sep 3, 2013 at 10:40 AM, David bouncingc...@gmail.com wrote:
On 4 September 2013 01:20, John McKown john.archie.mck...@gmail.com
wrote:
If you don't want to do a commit,
I get
eef5296 Thu Aug 15 16:37:35 2013 +0200 msg3
1e68ecb Wed Aug 14 11:08:22 2013 +0200 msg2
4959e91 Mon Jul 29 12:03:09 2013 +0200 msg1
with my locale
LANG=en_GB.UTF-8
LC_ALL=en_GB.UTF-8
Dne úterý, 3. září 2013 17:30:09 UTC+2 John McKown napsal(a):
See if:
git log --format=%h %cd %s
I know this is from several years ago, but did you ever come up with a
solution to this? I'm currently running into the same problem, using
dropbearkey and git through Terminal IDE on an ASUS android tablet. The
push works, but I get The remote end hung up unexpectedly and the
post-receive
Hello,
I'm kinds of new on Git and now we are trying to get the hooks enabled into
one of our server repository, what we want this hooks doing is to
prevent when local users that push the changes from their local repo to
server repo, we need to first check the commit comments to see if it
On Tuesday, September 3, 2013 8:07:06 PM UTC+5:30, William Seiti Mizuta
wrote:
Hi Dexter,
you are using option x in git clean command. In the manual, the option x
tells:
-x
Don’t use the standard ignore rules read from .gitignore (per
directory) and
Truckload of thanks for the explanation.
It must have taken a lot of iron wire to bend it for me. :-)
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
21 matches
Mail list logo
