2011-09-28 18:03:59 +00:00
|
|
|
{- git ls-tree interface
|
|
|
|
-
|
|
|
|
- Copyright 2011 Joey Hess <joey@kitenet.net>
|
|
|
|
-
|
|
|
|
- Licensed under the GNU GPL version 3 or higher.
|
|
|
|
-}
|
|
|
|
|
|
|
|
module Git.LsTree (
|
2011-09-28 20:43:10 +00:00
|
|
|
TreeItem(..),
|
2011-09-29 23:04:24 +00:00
|
|
|
lsTree,
|
|
|
|
parseLsTree
|
2011-09-28 18:03:59 +00:00
|
|
|
) where
|
|
|
|
|
|
|
|
import Numeric
|
|
|
|
import Control.Applicative
|
2011-09-28 18:14:52 +00:00
|
|
|
import System.Posix.Types
|
2011-09-29 23:04:24 +00:00
|
|
|
import qualified Data.ByteString.Lazy.Char8 as L
|
2011-09-28 18:03:59 +00:00
|
|
|
|
2011-09-30 03:43:42 +00:00
|
|
|
import Git
|
2011-12-13 19:22:43 +00:00
|
|
|
import qualified Git.Filename
|
2011-09-28 18:03:59 +00:00
|
|
|
import Utility.SafeCommand
|
|
|
|
|
|
|
|
data TreeItem = TreeItem
|
2011-09-28 18:14:52 +00:00
|
|
|
{ mode :: FileMode
|
2011-09-29 23:04:24 +00:00
|
|
|
, typeobj :: String
|
2011-09-28 18:03:59 +00:00
|
|
|
, sha :: String
|
|
|
|
, file :: FilePath
|
|
|
|
} deriving Show
|
|
|
|
|
improve type signatures with a Ref newtype
In git, a Ref can be a Sha, or a Branch, or a Tag. I added type aliases for
those. Note that this does not prevent mixing up of eg, refs and branches
at the type level. Since git really doesn't care, except rare cases like
git update-ref, or git tag -d, that seems ok for now.
There's also a tree-ish, but let's just use Ref for it. A given Sha or Ref
may or may not be a tree-ish, depending on the object type, so there seems
no point in trying to represent it at the type level.
2011-11-16 06:23:34 +00:00
|
|
|
{- Lists the contents of a Ref -}
|
|
|
|
lsTree :: Ref -> Repo -> IO [TreeItem]
|
2011-11-08 19:34:10 +00:00
|
|
|
lsTree t repo = map parseLsTree <$>
|
improve type signatures with a Ref newtype
In git, a Ref can be a Sha, or a Branch, or a Tag. I added type aliases for
those. Note that this does not prevent mixing up of eg, refs and branches
at the type level. Since git really doesn't care, except rare cases like
git update-ref, or git tag -d, that seems ok for now.
There's also a tree-ish, but let's just use Ref for it. A given Sha or Ref
may or may not be a tree-ish, depending on the object type, so there seems
no point in trying to represent it at the type level.
2011-11-16 06:23:34 +00:00
|
|
|
pipeNullSplitB [Params "ls-tree --full-tree -z -r --", File $ show t] repo
|
2011-09-28 18:03:59 +00:00
|
|
|
|
|
|
|
{- Parses a line of ls-tree output.
|
|
|
|
- (The --long format is not currently supported.) -}
|
2011-09-29 23:04:24 +00:00
|
|
|
parseLsTree :: L.ByteString -> TreeItem
|
2011-09-30 02:31:20 +00:00
|
|
|
parseLsTree l = TreeItem
|
|
|
|
{ mode = fst $ head $ readOct $ L.unpack m
|
|
|
|
, typeobj = L.unpack t
|
|
|
|
, sha = L.unpack s
|
2011-12-13 19:22:43 +00:00
|
|
|
, file = Git.Filename.decode $ L.unpack f
|
2011-09-30 02:31:20 +00:00
|
|
|
}
|
2011-09-28 18:03:59 +00:00
|
|
|
where
|
|
|
|
-- l = <mode> SP <type> SP <sha> TAB <file>
|
2011-09-29 23:04:24 +00:00
|
|
|
-- All fields are fixed, so we can pull them out of
|
|
|
|
-- specific positions in the line.
|
|
|
|
(m, past_m) = L.splitAt 7 l
|
|
|
|
(t, past_t) = L.splitAt 4 past_m
|
|
|
|
(s, past_s) = L.splitAt 40 $ L.tail past_t
|
|
|
|
f = L.tail past_s
|