1,429 reputation
413
bio website linkedin.com/in/aleschinsky
location Russia
age 48
visits member for 2 years, 7 months
seen Feb 25 at 4:04

Admin, programmer, PM, dreamer, postmaster, bummer, standpatter, misanthrope


Nov
17
awarded  Good Answer
Sep
18
awarded  Yearling
Jul
27
awarded  Nice Answer
Jul
27
revised Strategy for keeping secret info such as API keys out of source control?
formatting
Jul
26
comment Maintaining SVN history for a file when merge is done from the dev branch to trunk?
@Sam - --search isn't cross-branch history - it's (as written) just search inside log-data. You can parse pre-1.8 logs for the same results, but it must be your own code
Jul
25
answered Maintaining SVN history for a file when merge is done from the dev branch to trunk?
Jul
24
comment Strategy for keeping secret info such as API keys out of source control?
@shabunc - RTFM! Ignored file not stored in repo
Jul
21
answered Source control and compilation tool chain
Jul
21
comment Source control and compilation tool chain
@jozefg - you just can't use SVN properly, it is not much worse in team-work, than (any) DVCS, in most (!!!) aspects
Jul
21
answered Strategy for keeping secret info such as API keys out of source control?
Jul
4
revised Best practices for merging a new version of third party source into an old version you've made changes to
typo
Jul
4
answered Best practices for merging a new version of third party source into an old version you've made changes to
May
21
answered CMS updates into subversion -> review process
May
1
answered Distributed SVN?
Apr
22
answered Release Management Tools with DVCS (Mercurial)
Apr
17
answered Possible solutions for sharing working copy of project between multiple computers?
Apr
13
comment Manage version control with a central development server (LAMP)
@MarcelGwerder - another systems are not better for your purpose (any SCM with good merging will satisfy you, and Git's merge /in common sense/ is better than svn's), they can give you just less headache and more easier learning curve, than Git. I touched Git, I use Subversion and Mercurial, without strong reasoning I'll never select Git as SCM of my choice (SVN for linear history and minimal concurrent changes, Mercurial in any more hard case)
Apr
13
answered Manage version control with a central development server (LAMP)
Mar
25
comment To integrate git versions as build numbers or not?
Just note: hash in it describe (last part of string) is not cset-id of tag, but hash of changeset, for which we get describe. In human-readable form v1.1.2-6-a3b27gae will be "Six changesets after changeset, tagged as v1.1.2-6, has short changeset-hash a3b27gae"
Mar
18
comment Release Management Tools with DVCS (Mercurial)
"The downside is that I do not think there is a TortoiseHG mode where you can see what branches are still unmerged" - there is Filter Toolbar (with correct revset it will show heads of still-not-merged branches)