branches around. The variable name can be modelled on the
>> various other FETCH_HEAD MERGE_HEAD and various others).
>>
>> So have a think about broader options...
>>
>> Philip
>>
>
> --
> You received this message because you are subscribed to
ccessfully used a lot.
Let git be one of such a tool for you.
--
Serge Matveenko
mailto: se...@matveenko.ru
github: http://lnkfy.com/1
linkedin: http://lnkfy.com/S
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubs
nning "git rm -rf ." from the top level of the
working tree. Afterwards you will be ready to prepare your new files,
repopulating the working tree, by copying them from elsewhere,
extracting a tarball, etc.
--
Serge Matveenko
mailto: se...@matveenko.ru
github: http://lnkfy.com/1
linkedin
eclipse.org/EGit/User_Guide#Possible_merge_results
--
Serge Matveenko
mailto: se...@matveenko.ru
github: http://lnkfy.com/1
linkedin: http://lnkfy.com/S
or now)
and
https://launchpad.net/~git-core/+archive/candidate for rc (1.8.1 already)
--
Serge Matveenko
mailto: se...@matveenko.ru
github: http://lnkfy.com/1
linkedin: http://lnkfy.com/S
--
use"
> with external developers having an SSH connection to the "git server".
You may be interested in using gitolite
https://github.com/sitaramc/gitolite to host your repositories "in
house". The setup is easy and you will get many features that github
has.
--
Serge Matveenko
mailto: se...@matveenko.ru
github: http://lnkfy.com/1
linkedin: http://lnkfy.com/S
--
emented maybe in a future version ?
You may put .gitignore in such a directory containing:
*
!.gitignore
It will add .gitignore and will never add anything under this dir.
--
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linkedin.com/in/sergematveenko
--
You rec
k and
will not have "tmp" branch in main repo.
It is good practice to include your username in the name of such
temporary branch, e.g. "owen-tmp", if you are not the only person who
uses that repo. But it completely depends on the your branch naming
convention.
--
Serge Matveenko
ork as expected. Thus the only
safe that is easy enough is to never use Dropbox to store git
repositories. Use github, your own hosted repo (e.g. use gitolite to
admin it), or just use bare repo stored somewhere on remotely accessed
machine via regular ssh.
--
Serge Matveenko
se...@matveenko.ru
http:
On Tue, Jul 24, 2012 at 3:18 AM, Łukasz Siwiński wrote:
> Ps: after: "$ echo dir alias='ls' >> .bashrc" exit & relaunch your
> prompt (bach/command line)
alias dir='ls -Alh'
gives more familiar look for windows user
personally I use this alias
On Thu, Jul 12, 2012 at 6:32 PM, Thomas Ferris Nicolaisen
wrote:
> In essence, checkout is the equivalent of what some other systems call
> "revert", and you have to get used to treating it with respect (as with any
> git command).
IMHO, it looks more like "switch" u
ng to checked out commit now really.
You've just checked out a commit as your HEAD that is the head of the
origin/master branch. But you need to checkout a new branch master
that will be a copy (local fork) of the origin/master or more probably
you need to checkout your existing master and merge orig
On Wed, Jun 20, 2012 at 11:43 AM, paymaster wrote:
> How can I know commit size?
What is size? A number of lines affected? Raw patch size in bytes?
Compressed patch size in bytes? Mount of data transferred via push
maybe?
--
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/
m/code/source-control/git/our-simple-git-workflow/
There are infinite number of the possible git workflow schemes you are
free to implement.
--
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linkedin.com/in/sergematveenko
--
You received this message because you are
deploy your code from central
repo (like github). It's fine for development or testing server. But
its usually better to use special deployment mechanisms for production
servers if you need to build or test your code before deploying.
I advise you to read http://en.wikipedia.org/wiki/Continuous
" or set GIT_MERGE_AUTOEDIT environment
variable to "no".
Consult http://git-scm.com/docs/git-pull and http://git-scm.com/docs/git-merge
P.S.: It is better to do write some messages on merging though.
--
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linked
our local reviewing into local
history state
2. git reset --hard origin/ # this to reset your local
checkouted branch to the central repo state
Repeat step 2 for every branch you want to reset into central repo
state after checkouting each corresponding local branch
--
Serge Matveenko
se...@matveenk
with
this line. look on to the minus sign.
--
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linkedin.com/in/sergematveenko
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to th
her will thank you
later when central repo will crash or you will guide somebody over
series of "git blame, git bisect, git rebase or git filter-branch".
By the way there is very useful video for getting people know benefits
of git better.
http://www.youtube.com/watch?v=4XpnKHJAok8 "Tec
Hi all!
Just want to notice once that there is mailing list for Russian
speaking users at
https://groups.google.com/forum/?fromgroups#!forum/russian-git
Sorry if this message bothers you. I just think that it will be useful
for some of this mailing list subscribers.
--
Serge Matveenko
se
20 matches
Mail list logo
