Re: [git-users] git rm ./

2013-09-11 Thread Jimit Modi
Wow. We Love you GIT :).

--
Jim(y || it)




On Thu, Sep 12, 2013 at 2:18 AM, superjag superja...@gmail.com wrote:

 Many thanks.

 In short, to recover a file deleted by git rm, use git fsck --unreachable to
 show the files git is holding in limbo, and then use git show $sha1name 
 filename to save each one back to your filesystem (where $sha1name is the
 blob ID shown in git fsck, and filename is the desired name of the file to
 save it in).

 Now I'm off to make that first commit...

  - Jonathan Graef

 On Wednesday, September 11, 2013 2:14:19 PM UTC-5, Konstantin Khomoutov
 wrote:

 On Wed, 11 Sep 2013 11:43:24 -0700 (PDT)
 superjag super...@gmail.com wrote:

  Silly me, I thought this would remove the project directory from the
  staging area, but no, it has to delete the entire project. I was
  still staging my first commit when my project got deleted, so I can't
  roll back.
 
  I found this:
  https://groups.google.com/**forum/#!topic/msysgit/**TLmc2996nWYhttps://groups.google.com/forum/#!topic/msysgit/TLmc2996nWY
 
  But while I can see my files in some kind of command-line editor, I
  can't save them. ESC:w just makes a beeping noise. Any ideas?
 
  I'm running git under Windows.

 Uh... If I can see my files in some kind of command-line editor, I
  can't save them. ESC:w just makes a beeping noise. means
 I have run `git show $sha1_name_as_shown_by_git_**fsck` and this
 command
 showed me the contents of my file in some kind of command-line editor
 then it's just Git spawned the so-called pager which, unless
 reconfigured by the user (you) in one way or another defaults to the
 program named less [1] which is distributed with Git for Windows.

 A pager consumes what another program sends to its standard input
 stream (this program is Git in our case) and allows the user to
 conveniently (okay, let's not discuss this aspect for a moment) view
 this input -- sort of read-only ad-hoc Notepad.

 less is ubiquitous in the Unix world but is certainly able to capture
 a Windows user by surprise.  To quit less just press the q key (for
 *q*uit), and to move the viewport use the page up/page down and cursor
 keys.  less is quite versatile -- hit the h key while in it to read its
 online help page.

 But back to your problem...  The final answer to the thread you
 referred to assumed you're familiar with command line, and supposed
 that you know about stream redirections supported by it.  Specifically,
 if a program prints something to its output, you're able to save this
 output by redirecting it to a file, like this:

 git show $sha1name  filename

 The  filename (also could be spelled without the white space --
 filename) is the crucial bit -- it would make `git show` to write
 whatever it prints to the file filename.

 Git took your by surprise because it tries to be smart and if it
 detects it was run on an interactive terminal and the output it's about
 to print is larger than the height of this terminal, it spawns the
 configured or default pager and sends its output there.  If it detects
 its output is redirected by the shell (that  filename thing) it just
 prints what it should print, and this output ends up being written into
 that file.

 See also [2].

 1. 
 http://en.wikipedia.org/wiki/**Less_%28Unix%29http://en.wikipedia.org/wiki/Less_%28Unix%29
 2. 
 https://groups.google.com/d/**msg/git-users/nn3f6FVMSNw/**NryIUTdKvFYJhttps://groups.google.com/d/msg/git-users/nn3f6FVMSNw/NryIUTdKvFYJ

  --
 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 git-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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 git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [git-users] Branch level authentication

2013-08-16 Thread Jimit Modi
Thanks. Will look at it and update.

--
Jim(y || it)




On Fri, Aug 16, 2013 at 1:10 PM, Gergely Polonkai gerg...@polonkai.euwrote:

 Hello,

 git itself is not capable of authentication and authorization, you will
 need a separate software for that. I personally use gitosis, but many
 others exist out there. This kind of software is needed only on the
 server side, clients can still use good old git client.

 Best,
 Gergely
 On 16 Aug 2013 06:46, Jimit Modi jimy2004k...@gmail.com wrote:

 At our company, we are evaulating to migrate to GIT from SVN. Here we
 are following a process in which we have the following branch and access
 control.

 ---
 | Branch| Purpose  | ACL  |
 ---
 | `master`  | live copy| AGM  |
 ---
 | `staging` | staging copy | AGM, TL  |
 ---
 | 'dev` | development copy | AGM, TL, Devs|
 ---

 Now all devs create a feature branch from the dev branch and again merge
 it in dev when they have finished working and push it. Now TL review the
 work and cherry pick or merge dev in staging, depending on the sencario.
 If everything is well they push the changes on staging. Same is done by
 AGM's for master branch.
 We want that devs will be able to pull the changes from staging and
 master branch, but will not be able to push.

 So the question is:
 - How can we setup a authentication system where only the allowed one
 will be able to push.?

 --
 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 git-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.

  --
 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 git-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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 git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[git-users] Branch level authentication

2013-08-15 Thread Jimit Modi


At our company, we are evaulating to migrate to GIT from SVN. Here we are 
following a process in which we have the following branch and access 
control.

---
| Branch| Purpose  | ACL  |  
---
| `master`  | live copy| AGM  |  
---
| `staging` | staging copy | AGM, TL  |
---
| 'dev` | development copy | AGM, TL, Devs|
---

Now all devs create a feature branch from the dev branch and again merge it 
in dev when they have finished working and push it. Now TL review the work 
and cherry pick or merge dev in staging, depending on the sencario. If 
everything is well they push the changes on staging. Same is done by AGM's 
for master branch.
We want that devs will be able to pull the changes from staging and master 
branch, 
but will not be able to push.

So the question is:
- How can we setup a authentication system where only the allowed one will 
be able to push.?

-- 
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 git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.